Cisco Meraki End of Life (EOL) Dates & Support Timeline

Cisco Meraki lifecycle status — the real story

Cisco Meraki cloud-managed hardware: MX security appliances and SD-WAN (with the Z teleworker gateways and the vMX100 virtual appliance), MS switches, MR wireless access points, MV cameras and MG cellular gateways. Cycles are the product rows Meraki prints on its own End-of-Life (EOL) Products and Dates page (public, no login, last updated Sep 23, 2026), one cycle per printed row, so a model listed on its own row never inherits its series date (MS120-8FP, MS390-48UX2 and MS220-8 carry their own dates). Field mapping, as Cisco's ASA 5500-X page: support is Meraki's End-of-Sale Date (the last date to order); eol is the End-of-Support (EOST) date, 'the last date a product will be affirmatively supported by Cisco Meraki, typically five years following the EOS date'; the announcement date is carried as an extra field. Release dates are not published and are left null.

What happens between the two dates, in Cisco's EOL policy: Meraki 'typically provides support for a given product for a period of five (5) years after the EOS date', and after a model's firmware version restriction date 'engineering level support, if available, will only be provided for critical security vulnerabilities until the hardware reaches its EOST date'. After EOST Meraki 'may no longer issue firmware updates or patches for the legacy products' and cannot guarantee the device will keep connecting to the dashboard.

Next up: the MX84 reaches End-of-Support on October 31, 2026; the MX100 on February 1, 2027; the MX64 and MX64W on July 26, 2027; the vMX100 on December 22, 2027. The MR42, MR42E, MR52, MR53, MR53E, MR74, MR45, MR84 and MR33 access points ended July 21, 2026 and the MX65 and MX65W on May 28, 2026. Newly announced: the MX67C and MX68CW (announced August 27, 2026, end of sale November 27, 2026, End-of-Support November 30, 2031), the MS450-12 (end of sale October 29, 2026), and the MR36, MR36H, MR44, MR46 and MR46E (end of sale December 31, 2026, End-of-Support December 31, 2031).

Out of scope on the same page: MT sensors, Meraki Go (GS, GR, GX), Systems Manager, licences (LIC-, EAB-, E3N-), mounts, antennas, power supplies and injectors, the MS390 uplink module, the MC74 phone, and the original 2010-2012 Meraki mesh routers (Indoor, Mini, Solar, Wall Plug, OD2). KEV: no CISA KEV entry names Meraki (catalog 2026.10.08).

Cisco Meraki release and support pattern

Of the 84 release lines tracked, 41 are past end of life and 43 are still within support. The next scheduled end of life is MX84 on October 31, 2026 — 20 days from this build. The longest-supported line currently published is MS390-48UX2, to April 4, 2032.

Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.

What does Cisco Meraki end of life mean for your organization?

When a version of Cisco Meraki reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.

Organizations running EOL Cisco Meraki should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Your options when Cisco Meraki reaches end of life

There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.

How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.

Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.

Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.

Extended Support Options

If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Cisco Meraki versions. This is a bridge, not a permanent solution — plan your migration in parallel.

Related Products